Update parsing to the new collection dates page #21
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rusq
approved these changes
Nov 15, 2025
Contributor
Author
|
Awesome, thanks for merging. Will you so a release? |
Owner
|
Done! (Inb4 - pushed a tag blissfully, forgot that there's no release action on this repo.) |
|
Hi Laurence, thanks for fixing this! It's been broken for a while now. I just recently updated the container when I saw this update but I'm still getting an error. Do you guys know what this is about? When I try to do the default command I get the result |
Contributor
Author
|
Just looked in to it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey. I went to use this and found it was broken.
So I forked it and updated it to properly parse the new front end "new.aucklandcouncil.govt.nz".
Also added a dev container and removed the trailing slash from the endpoints which I think is more conventional (I got stuck on this for a while).
Also updated the home assistant bit to use rest instead of sensor.rest, so it will just make a single call to the API.
Anyway, I updated the unit tests, tested locally, and have it working integrated into my Home Assistant.